Systems and Methods to Selectively Authenticate via Mobile Communications

ABSTRACT

Systems and methods to accelerate transactions made via mobile communications. In one aspect, a system includes: a data storage facility to store information associated with past payment transactions and an interchange coupled with the data storage facility. The interchange includes a common format processor and a plurality of converters to interface with a plurality of controllers. The converters are configured to communicate with the controllers in different formats, and to communicate with the common format processor in a common format. After a payment request identifying the phone number is received in the interchange, the common format processor is to determine whether to skip mobile communications with a mobile phone at the phone number to confirm/authenticate the request, based on real time information about the current transaction, the historical transaction data related to the phone number, and other data such as social graph data related to the user of the phone number.

RELATED APPLICATIONS

The present application relates to U.S. patent application Ser. No. 12/406,084, filed Mar. 17, 2009 and entitled “Systems and Methods to Approve Electronic Payments,” and U.S. patent application Ser. No. 12/813,338, filed Jun. 10, 2010 and entitled “Systems and Methods to Accelerate Transactions,” the disclosures of which applications are incorporated herein by reference.

FIELD OF THE TECHNOLOGY

At least some embodiments of the disclosure relate to mobile communications in general and, more particularly but not limited to, mobile communications to facilitate online transactions.

BACKGROUND

Short Message Service (SMS) is a communications protocol that allows the interchange of short text messages between mobile telephone devices. SMS messages are typically sent via a Short Message Service Center (SMSC) of a mobile carrier, which uses a store-and-forward mechanism to deliver the messages. When a mobile telephone is not reachable immediately for the delivery of the message, the SMSC stores the message for later retry.

SMS messages can be sent via gateways. Some gateways function as aggregators. An aggregator typically does not have the capacity to deliver the messages directly to mobile phones. An aggregator typically interfaces with and relies upon the SMSC of a mobile carrier to deliver SMS messages.

Some gateways function as providers that are capable of sending text messages to mobile devices directly, without going through the SMSC of other mobile operators.

Text messaging between mobile telephones can also be performed using other protocols, such as SkyMail and Short Mail in Japan.

Some mobile carriers provide email gateway services to allow text messages to be sent to mobile phones via email. For example, a non-subscriber of the mobile carrier may send a message to an email address associated with a mobile phone of a subscriber of the mobile carrier to have the message delivered to the mobile phone via text messaging.

Emails can also be sent to mobile telephone devices via standard mail protocols, such as Simple Mail Transfer Protocol (SMTP) over Internet Protocol Suite (commonly TCP/IP, named from two of the protocols: the Transmission Control Protocol (TCP) and the Internet Protocol (IP)).

Short messages may be used to provide premium services to mobile phones, such as news alerts, ring tones, etc. The premium content providers may send the messages to the SMSC of the mobile operator using a TCP/IP protocol, such as Short Message Peer-to-Peer Protocol (SMPP) or Hypertext Transfer Protocol, for delivery to a mobile phone; and the mobile phone is billed by the mobile operator for the cost of receiving the premium content.

Premium services may also be delivered via text messages initiated from the mobile phone. For example, a televoting service provider may obtain a short code to receive text messages from mobile phones; and when the user sends a text message to the short code, the mobile carrier routes the message to the televoting service provider and charges the user a fee, a portion of which is collected for the televoting service provider.

SUMMARY OF THE DESCRIPTION

Systems and methods are provided to accelerate transactions made via mobile communications. Some embodiments are summarized in this section.

In one aspect, a system to accelerate the processing of a payment transaction includes a data storage facility to store information associated with past payment transactions and an interchange coupled with the data storage facility. The interchange includes a common format processor and a plurality of converters to interface with a plurality of controllers. The converters are configured to communicate with the controllers in different formats, and to communicate with the common format processor in a common format.

After a payment request identifying the phone number is received in the interchange, the common format processor is to determine whether to skip mobile communications with a mobile phone at the phone number to confirm/authenticate the request. In response to a determination to not skip the mobile communications for the confirmation/authentication of the request, the common format processor is to use one of the converters to communicate with the mobile phone at the phone number to confirm the request. In response to a determination to skip the mobile communications for the confirmation/authentication of the request, the interchange is to bill a user of the phone number using a funding source associated with the phone number without communicating with the mobile phone for the authorization of a payment to a merchant in accordance with the payment request.

In another aspect, a computer implemented method includes: receiving, in a computing device, a request to make a payment to a merchant using funds associated with a phone number; determining, using the computing device, whether to skip mobile communications with a mobile phone at the phone number to confirm the request; in response to a determination to not skip the mobile communications, communicating with the mobile phone at the phone number to confirm the request; and in response to a determination to skip the mobile communications, billing a user of the phone number using a funding source associated with the phone number without the communicating with the mobile phone.

The disclosure includes methods and apparatuses which perform these methods, including data processing systems which perform these methods, and computer readable media containing instructions which when executed on data processing systems cause the systems to perform these methods.

Other features will be apparent from the accompanying drawings and from the detailed description which follows.

BRIEF DESCRIPTION OF THE DRAWINGS

The embodiments are illustrated by way of example and not limitation in the figures of the accompanying drawings in which like references indicate similar elements.

FIG. 1 shows a system to facilitate online transactions according to one embodiment.

FIG. 2 shows an interchange to route messages according to one embodiment.

FIG. 3 shows a message processor according to one embodiment.

FIG. 4 shows a method to facilitate an online transaction using an interchange according to one embodiment.

FIG. 5 illustrates a user interface to associate an account with a telephone number according to one embodiment.

FIG. 6 illustrates another user interface to associate an account with a telephone number according to one embodiment.

FIG. 7 illustrates a user interface to initiate a payment transaction according to one embodiment.

FIG. 8 illustrates a user interface to initiate a payment request according to one embodiment.

FIG. 9 illustrates a user interface to confirm a payment request according to one embodiment.

FIG. 10 illustrates a user interface to confirm the completion of a payment transaction according to one embodiment.

FIG. 11 illustrates a way to redirect a payment confirmation according to one embodiment.

FIG. 12 illustrates a user interface to receive payment options according to one embodiment.

FIG. 13 shows a method to process an online payment according to one embodiment.

FIG. 14 shows another method to facilitate a payment transaction according to one embodiment.

FIGS. 15-18 show methods to approve a payment transaction according to some embodiments.

FIG. 19 illustrates a transaction database according to one embodiment.

FIG. 20 shows an arrangement to accelerate payments to a merchant according to one embodiment.

FIG. 21 shows a system to provide funds to a merchant according to one embodiment.

FIG. 22 shows a method to provide funds to a merchant according to one embodiment.

FIG. 23 shows a system to simplify and accelerate payment processing according to one embodiment.

FIG. 24 shows a method to simplify and accelerate payment processing according to one embodiment.

FIG. 25 illustrates a method to selectively skip authorization for mobile transactions according to one embodiment.

FIG. 26 shows a data processing system, which can be used in various embodiments.

DETAILED DESCRIPTION

The following description and drawings are illustrative and are not to be construed as limiting. Numerous specific details are described to provide a thorough understanding. However, in certain instances, well known or conventional details are not described in order to avoid obscuring the description. References to one or an embodiment in the present disclosure are not necessarily references to the same embodiment; and, such references mean at least one.

Reference in this specification to “one embodiment” or “an embodiment” means that a particular feature, structure, or characteristic described in connection with the embodiment is included in at least one embodiment of the disclosure. The appearances of the phrase “in one embodiment” in various places in the specification are not necessarily all referring to the same embodiment, nor are separate or alternative embodiments mutually exclusive of other embodiments. Moreover, various features are described which may be exhibited by some embodiments and not by others. Similarly, various requirements are described which may be requirements for some embodiments but not other embodiments.

In one embodiment, an interchange is used to interface with a plurality of different controllers of mobile communications, such as SMS messages. The interchange can be used to associate account information with phone numbers to facilitate electronic payments via mobile devices, such as mobile phones or cellular phones. The interchange is configured to communicate with the mobile phones through the different controllers to provide security and convenience for online transactions.

FIG. 1 shows a system to facilitate online transactions according to one embodiment. In FIG. 1, an interchange (101) is provided to interface with a plurality of different controllers (115) for communications with the mobile phones (117) over the wireless telecommunications network (105).

In FIG. 1, a data storage facility (107) stores user account information (121) and the corresponding phone numbers (123) of the mobile phones (117). The interchange (101) is coupled with the data storage facility (107) to communicate with the mobile phones (117) at the corresponding phone numbers (123) to confirm operations that are performed using the account information (121). Since the account information (121) is secured by the interchange (101), the account information (121) can be used to pay for products and services offered by the servers (113) of various merchants, without being revealed to the merchants.

In one embodiment, the server (113) offers products and/or services adapted for a virtual world environment, such as an online game environment, a virtual reality environment, etc. The products may be virtual goods, which can be delivered via the transmission of data or information (e.g., without having to physically deliver an object to the user). For example, the virtual goods may be a song, a piece of music, a video clip, an article, a computer program, a decorative item for an avatar, a piece of virtual land in a virtual world, a virtual object in a virtual reality world, etc. For example, an online game environment hosted on a server (113) may sell services and products via points or virtual currency, which may be consumed by the user while engaging in a game session. For example, a virtual reality world hosted on a server (113) may have a virtual currency, which may be used by the residents of the virtual reality world to conduct virtual commerce within the virtual reality world (e.g., buy virtual lands, virtual stocks, virtual objects, services provided in the virtual reality world, etc.). In other embodiments, the server (113) may also offer physical goods, such as books, compact discs, photo prints, postcards, etc.

In FIG. 1, the interchange (101) may communicate with different controllers (115) of mobile communications via different networks (e.g., 105 and 103) and/or protocols. The interchange (101) processes the requests in a common format and uses a set of converters for communications with the different controllers (115) respectively.

For example, the controllers (115) may be different aggregators, providers and/or SMSCs of different mobile carriers. Based on the phone numbers (123), the interchange (101) interfaces with the corresponding controllers (115) to communicate with the mobile phones (117) via text messaging to confirm the operations related to the corresponding account information (121), such as bank accounts, credit card numbers, charge card numbers, etc.

In FIG. 1, the user terminals (111) may use a unified interface to send requests to the interchange (101). For example, a web site of the interchange (101) may be used to receive the account information (121) from the web browsers running in the user terminals (111). The user terminals (111) are typically different from the mobile phones (117). However, in some embodiments, users may use the mobile phone (117) to access the web and submit the account information (121). Alternatively, the users may use the mobile phone (117) to submit the account information (121) to the interchange (101) via text messaging, email, instant messaging, etc.

The use of the mobile phones (117) in the confirmation of activities that involve the account information (121) increases the security of the transaction, since the mobile phones (117) are typically secured in the possession of the users.

Further, in one embodiment, the interchange (101) may use the phone bills of the mobile phones (117) to pay for purchases, in order to use the account information (121) to pay for the phone bills, and/or to deposit funds into the accounts identified by the account information (121) by charging on the phone bills of the corresponding mobile phones (117). In some embodiments, the accounts identified by the account information (121) are hosted on the data storage facility (107). In other embodiments, the accounts are hosted on the account servers (125) of financial institutions, such as banks, credit unions, credit card companies, etc.

In one embodiment, once the account information (121) is associated with the mobile phones (117) via their phone numbers (123) stored in the data storage facility (107), the users may use the user terminals (111) to access online servers (113) of various merchants or service providers to make purchases. From the user terminals (111), the users can use the accounts identified by the account information (121) to make the payment for the purchases, without revealing their account information (121) to the operators of the servers (113).

In one embodiment, the mobile phones (117) are used by the corresponding users to make payments and/or manage funds, such as for making purchases on various websites hosted on the servers (113) of merchants and service providers and/or for transferring funds to or from an account identified by the account information (121), such as phone bills for land-line telephone services, credit card accounts, debit card accounts, bank accounts, etc., or an account hosted on the data storage facility (107) or telecommunication accounts of the mobile phones (117) with telecommunication carriers. The mobile phones (117) are used to confirm and/or approve the transactions associated with the account identified by the account information (121) (or other accounts). The interchange (101) interfaces the mobile phones (117) and the servers (113) to confirm and/or approve transactions and to operate on the account identified by the account information (121) (and/or other accounts associated with the phone number (123)).

For example, the user terminal (111) may provide the phone number (123) to the servers (113) to allow the servers (113) to charge the account identified by the account information (121) associated with the phone number (123). The interchange (101) sends a message to the mobile phone (117) via the phone number (123) to confirm the payment request. Once the payment is confirmed or approved via the corresponding mobile phone (117), the interchange (101) charges the account identified by the account information (121) (e.g., by communicating with the account server (125) on which the corresponding accounts are hosted) and pays the server (113) on behalf of the user, using the funds obtained from the corresponding account identified by the account information (121).

In one embodiment, the user terminal (111) may not even provide the phone number (123) to the server (113) to process the payment. The server (113) may redirect a payment request to the interchange (101), which then prompts the user terminal (111) to provide the phone number (123) to the web site of the interchange (101) to continue the payment process.

For example, the server (113) may redirect the payment request to the web site of the interchange (101) with a reference indicating the purchase made via the user terminal (111). The interchange (101) can use the reference to subsequently complete the payment with the server (113) for the purchase, after receiving the phone number (123) directly from the user terminal (111) to confirm the payment via the mobile phone (117).

In some embodiments, instead of directly providing the phone number (123) to identify the account information (121), the user may provide other information to identify the phone number (123), such as an account identifier of the user assigned to the user for obtaining the services of the interchange (101).

In one embodiment, the account information (121) is pre-associated with the phone number (123) prior to the payment request. The account information (121) may be submitted to the interchange (101) via the user terminal (111) or the mobile phone (117) via a secure connection.

Alternatively, the user may supply the account information (121) to the interchange (101) at the time the payment request is submitted from the user terminal (111) to the interchange (101). Alternatively, the user may supply the account information (121) to the interchange (101) at the time the user responds to the confirmation message for the payment request.

In some embodiments, the user may supply the account information (121) after a transaction using funds collected via the telecommunication carrier of the mobile phone (117) at the phone number (123). For example, after the transaction, the interchange (101) may send an invitation message, such as a text message to the mobile phone (117) at the phone number (123), to the user to invite the user to register with the interchange (101) and provide the account information (121). The user may register with the interchange (101) via the mobile phone (117) (e.g., by a replying text message), or via a web page of the interchange (101) (e.g., using a link and/or a unique code provided in the invitation message).

After the user registers with the interchange (101) (e.g., via the mobile phone (117) and by providing the account information (121)), the user may create a customized personal identification number (PIN) or receive a PIN for enhanced security. Using the PIN, the user may use the account information (121) to complete an online transaction without having to confirm and/or approve a transaction using the mobile phone (117). In some embodiments, the PIN may be used to reduce unwanted messages to the mobile phone (117). For example, once the phone number (123) and the account information (121) are associated with a PIN, the interchange (101) may require the user of the user terminal (111) to provide the correct PIN to initiate the payment process. Thus, a spammer having only the phone number (123) (or a different user mistakenly using the phone number (123)) may not successfully use the user terminal (111) to request the interchange (101) to send confirmation messages to the mobile phone (117) protected by the PIN. In some embodiments, the interchange (101) may offer further incentives to the user for registering with the interchange (101), such as reduced fees, discounts, coupons, free products and services, etc.

In one embodiment, once the account information (121) is associated with the phone number (123) in the data storage facility (107), the user does not have to resubmit the account information (121) in subsequent payment requests.

By delegating the payment task to the interchange (101) and securing the account information (121) in the data storage facility (107), the system as shown in FIG. 1 can increase the security of using the account information (121) in an online environment.

In some embodiments, the interchange (101) can also fulfill the payment requests using the funds collected via the phone bill of the phone numbers (123). The interchange (101) can collect the funds via sending premium messages to the mobile phones (117) at the phone numbers (123), after receiving confirmation from the mobile phone (117).

For example, after the confirmation or approval message is received from the mobile phone (117), the interchange (101) performs operations to collect funds via the phone bill of the phone number (123). The interchange (101) may calculate the required premium messages to bill to the mobile phone (117). For example, mobile terminated premium SMS messages may have a predetermined set of prices for premium messages. The interchange (101) determines a combination of the premium messages that has a price closest to the amount required by the transaction, and sends this combination of premium messages to the mobile phone (117). For example, mobile originated premium SMS messages may also have a predetermined set of prices for premium messages. The interchange (101) can calculate the set of messages required for the transaction and transmit a text message to the mobile phone (117) of the user to instruct the user to send the required number of premium messages to provide the funds.

In one embodiment, the data storage facility (107) stores the transaction history (127) associated with the phone number (123) and uses the transaction history (127) to approve payment requests and to reduce the time period for processing a subsequent payment request.

For example, from the transaction history (127) the interchange (101) may identify a pattern of prior payment requests made via the phone number (123) and match subsequent requests with the identified pattern. When a subsequent request matches the pattern, the interchange (101) may skip the communication with the mobile phone (117) at the phone number (123), which communication is otherwise performed after the payment request and before the payment operation for payment confirmation and/or approval. Skipping such a communication between the payment request and the payment operation can reduce the time period for payment processing and improve user experience.

Examples of transaction patterns may include the use of individual user terminals (111), the typical time period of payment requests, range of payment amounts, and/or certain characteristics of payees, such as a collection of frequently used payees, payees who provide certain types of products or services, the geographical region of payees, etc.

In one embodiment, when the subsequent payment request is received within a predetermined time limit of a previous confirmed payment request from the same user terminal (111), the interchange (101) may approve the payment request without communicating with the mobile phone (117) at the phone number (123) for approval or confirmation.

In one embodiment, when the interchange (101) skips the communication with the mobile phone (117) at the phone number (123) for approval or confirmation and approves a transaction request based on the transaction history (127), the interchange (101) may send a notification message to the mobile phone (117) at the phone number (123) for enhanced security, but not require a response from the user. If the user determines that the notification message corresponds to an unauthorized use of the phone number (123), the user may reply to the notification message from the mobile phone (117) to report the unauthorized use and/or stop or reverse the payment operation.

In some embodiments, the user may start a session (e.g., a web session) authenticated using a password associated with the phone number (123) prior to the payment request. When the payment request is made within the authenticated session (e.g., before the user logs off the session, or before the session times out), the interchange (101) may skip the confirmation/approval communication with the mobile phone (117) at the phone number (123) to reduce the time period for payment processing.

In one embodiment, the session is authenticated via communications with the mobile phone (117) at the phone number (123). For example, after the user provides the phone number (123) to log into a session on a user terminal (111), the interchange (101) may generate a code (e.g., a code for one time use) and send the code to the user via the user terminal (111) (or the mobile phone (117) at the phone number (123)). The interchange (101) then requests the code back from the user via the mobile phone (117) at the phone number (123) (or the user terminal (111)), which is not used to send the code. When the code sent by the interchange (101) matches the code received back from the user, the association between the user terminal (111) and the mobile phone (117) at the phone number (123) can be established; and the identity of the user of the user terminal (111) can be confirmed. Such confirmation can be logged in the transaction history (127) for subsequent approval of payment requests.

In one embodiment, the user may specify a time period for the session, or the time period for the association between the user terminal (111) and the phone number (123). The user may specify the time period using the user terminal (111) when providing the phone number (123) to initiate the session, or specify the time period using the mobile phone (117) when providing the one-time code back to the interchange (101). During the time period of the confirmed association between the user terminal (111) and the phone number (123), a payment request from the user terminal (111) can be automatically identified with the phone number (123) without the user having to explicitly specify the phone number (123) for the payment request. Alternatively, for enhanced security and/or flexibility, the interchange (101) may require the user to identify the phone number (123) in the payment request, even though the payment request is from the user terminal (111) that is associated with the phone number (123).

In one embodiment, the code for the authentication of the session can be communicated to and/or from the mobile phone (117) via short message service (SMS), voice message, voice mail, or other services, such as email, instant messaging, multimedia messaging service (MMS), etc.

In one embodiment, after the user provides the phone number (123) to log into a session on a user terminal (111), the interchange (101) provides a message to the mobile phone (117) at the phone number (123) and receives a reply to the message from the mobile phone (117) within a predetermined period of time to authenticate the session and associate the user terminal (111) with the phone number (123). If the reply is not received from the mobile phone (117) with the predetermined period of time, the session is not authenticated.

In one embodiment, the user may provide an advance approval for subsequent payment requests to pay via the phone number (123). The advance approval may include a number of limitations, such as the time limit for the expiration of the advance approval, the budget limit for the advance approval, a limit on payees for the advance approval, etc. For example, the advance approval may limit the payees based on their business category, web address, product type, service type, geographic location, etc. For example, the budget limit may include the frequency of subsequent payment requests, limits for individual payment requests, and a total limit for subsequent payment requests, etc.

In one embodiment, the advance approval is specific for a user terminal. For example, the advance approval may be obtained via communications with the user via both a specific user terminal (111) and the mobile phone (117) at the phone number (123). Thus, the advance approval applies only to subsequent payment requests from the specific user terminal (111) identified by the advance approval.

Alternatively, the advance approval may not be limited to a specific user terminal (111). The advance approval may be used for any user terminals (111) used by the user of the phone number (123) to request payments via the phone number (123). In some embodiments, the advance approval is limited to user terminals (111) of certain characteristics identified by the advance approval, such as a geographic region of the user terminal (111) (e.g., determined based on the communication addresses, routing paths, access points for wireless connections, base stations for cellular communications, etc.). In some embodiments, the interchange (101) automatically identifies these characteristics based on the communications to obtain the advance approval (e.g., based on transaction history (127)), without the user explicitly specifying the characteristics.

FIG. 2 shows an interchange to route messages according to one embodiment. In FIG. 2, the interchange (101) includes a unified data interface (135) for interaction with the servers (113). The servers (113) may redirect the payment requests to the interchange (101) to allow the interchange (101) to subsequently communicate with the user to process the payment request, including obtaining payment options and identifying user account information (121), before returning to communicating with the server (113). Alternatively, the servers (113) may collect account related information (e.g., the phone number of the user) to request payment from the interchange (101).

In FIG. 2, the interchange (101) includes a common format processor (133), which processes various payment options in a common format. In one embodiment, the common format processor (133) can handle the payments via mobile terminated text message, mobile originated text message, operator billing, credit card, stored value account, and other online payment options. The common format processor (133) determines the actual amount that is to be billed to the user, based on the payment options (e.g., mobile terminated premium SMS, mobile originated premium SMS, operator billing, credit cards, etc.), and selects a converter (131) to communicate with a corresponding controller (115).

Different converters (131) are configured to communicate with corresponding controllers (115) in different languages and protocols. The converters (131) perform the translation between the common format used by the common format processor (133) and the corresponding formats used by the controllers (115).

The use of the common format processor (133) simplifies the structure of the interchange (101) and reduces the development effort required for the interchange (101) to interface with the increasing number of different controllers, such as SMSC, mobile providers, aggregators, gateways, etc.

FIG. 3 shows a message processor according to one embodiment. In FIG. 3, the common format processor (133) includes a billing engine (157) that calculates the amount to be billed to the user, by adding or subtracting transaction costs for different billing methods, such as mobile terminated text message, mobile originated text message, operator billing, credit card, stored value account, and other online payment options.

In one premium message billing method, the interchange (101) sends mobile terminated premium SMS messages to the mobile phone (117) to bill the user, or requests the mobile phone (117) to send mobile originated premium SMS messages to a short code representing the interchange (101).

In one operator billing method, the interchange (101) directly sends a message to the mobile carrier of the mobile phone (117) to bill the amount on the phone bill of the mobile phone (117), without having to send a premium message to the mobile phone (117).

The common format processor (133) includes a decision engine (151) which decides how to generate a set of one or more messages to the mobile phone (117) based on a set of rules (141), regulations (143), limits (145), records (147) and restrictions (149).

For example, different countries have different regulations (143) governing mobile communications with the mobile phones (117). For example, different mobile carriers have different rules (141) regarding premium messages. For example, past transaction records (147) can be used to monitor the transactions to discover suspected fraudulent activities. For example, parental limits (145) and merchant restrictions (149) can be imposed.

Based on results of the decision engine (151), the mobile message generator (153) generates one or more messages to communicate with the mobile phone (117) about the transaction (e.g., a request to collect funds via the phone bill of the user for a payment request, or for deposit into an account identified by the account information (121)). The converter (131) then interfaces with the corresponding controller (115) to transmit the messages to the mobile phone (117).

FIG. 4 shows a method to facilitate an online transaction using an interchange according to one embodiment. In FIG. 4, the user terminal (111) provides (171) account information (121) to the interchange (101) for association with the phone number (123). For example, the user may use a device running a web browser as the user terminal (111) to submit the account information (121) via a secure web connection. The user terminal (111) is typically different from the mobile phone (117). However, in some embodiments, the mobile phone (117) may also be used as the user terminal (111) to submit the account information (121) (e.g., via a wireless application protocol (WAP) application, or via a message sent via short message service (SMS) or multimedia message service (MMS), or via an email message or an instant message).

After the user provides the account information (121) to the interchange (101) for storage in the data storage facility (107), the user can send (177) a charge request to the server (113) of a merchant from the user terminal (111). The server (113) of the merchant can send or redirect (179) the charge request to the interchange (101). In response to the charge request, the interchange (101) sends (173) a confirmation message to the mobile phone (117). If the user sends (173) an approval, or an appropriate reply, to the confirmation message from the mobile phone (117), the interchange (101) communicates with the account server (125) to charge an account of the user identified by the account information (121), without revealing the account information (121) to the server (113). The interchange (101) pays the merchant on behalf of the user using the funds collected via charging the account of the user. For example, the interchange (101) may use its own bank account to pay the merchant operating the server (113). Thus, the financial information of the user is not revealed to the merchant.

Upon the completion of the payment process, the interchange (101) can notify the user via the mobile phone (117) and/or the user terminal (111).

In some embodiments, the server (113) of the merchant redirects the charge request to allow the user terminal (111) to communicate with the interchange (101) to continue the payment process; and the user terminal (111) may provide (171) the account information (121) directly to the interchange (101) after the charge request is redirected.

In alternative embodiments, the user may provide the account information (121) from the mobile phone (117) together with the approval of the charge request.

In one embodiment, the interchange (101) communicates with the mobile phone (117) for the confirmation of the charge request via SMS messages. Alternatively, the confirmation and approval messages can be sent (173) via emails, instant messages, voice message, live calls from operators, etc.

In some embodiments, the user of the mobile phone (117) may choose to fulfill the charge request via the phone bill, instead of charging the account identified by the account information (121). Thus, after the confirmation, the interchange (101) sends the premium messages to the mobile phone (117) to collect funds via the phone bill of the mobile phone (117). In other embodiments, the interchange (101) may send an instruction with the confirmation message to the mobile phone (117) to instruct the user to send mobile originated premium messages to the interchange (101) to collect the funds via the phone bill of the mobile phone (117).

FIG. 5 illustrates a user interface to associate an account with a telephone number according to one embodiment. In FIG. 5, the user interface (180) includes a text field (183) that allows the user to specify the phone number (123) with which the account information (121) provided in the text field (181) is to be associated.

In FIG. 5, the user interface (180) further includes an option list, which allows the user to select various types of accounts, such as credit card accounts, bank accounts, charge card accounts, etc. In the example illustrated in FIG. 5, the checkbox (185) is selected to specify a credit card account.

In some embodiments, the user interface (180) may further present a text field (not shown in FIG. 5) to allow the user to specify an alias for the account information (121) supplied in the text input field (181). For enhanced security, the alias can be used for subsequent communications with the user without revealing the account information (121).

In FIG. 5, the user interface (180) may be presented via a web browser (or a custom application) to submit account information (121) in the text input field (181) from a user terminal (111) to the interchange (101). Alternatively, the account number can be submitted from the mobile phone (117) via a message sent via SMS, WAP, voice mail, or via an interactive voice response (IVR) system.

In one embodiment, the server (113) presents the payment option (185) via an online shopping cart system or a third party checkout system. Alternatively, or in combination, the server (113) presents the payment option (185) via a web widget. For example, a web widget may include a program code that is portable and executable within a web page without requiring additional compilation. The web widget allows the user to select the option (185) to pay for the product and/or service without leaving the web page or refreshing the web page. In one embodiment, the interchange (101) provides the web widget to facilitate the payment processing.

FIG. 6 illustrates another user interface to associate an account with a telephone number according to one embodiment. In FIG. 6, the user interface (190) is presented on the mobile phone (117) of the user. The user interface (190) presents a message (191) from the interchange (101) to the mobile phone (117) at the phone number (123). The message (191) prompts the user to submit the account information (121) by providing a reply message (193). The user may select the “send” button (195) to provide the account information (121) for association with the phone number (123) or select the “cancel” button (197) to ignore the prompt.

In one embodiment, the messages (191 and 193) are transmitted to the mobile phone (117) via a short message service (SMS). Alternatively, the messages can be transmitted to the mobile phone (117) via other protocols, such as multimedia message service (MMS), email, instant messaging, WAP, voice mail, voice messages via an interactive voice response (IVR) system, etc.

FIG. 7 illustrates a user interface to initiate a payment transaction according to one embodiment. In FIG. 7, the user interface (201) provides an option (205) to request the interchange (101) to process the payment for the amount (203) required to make a purchase from the server (113) of a merchant.

In one embodiment, after the user selects the payment option (205), the server (113) directs the request to the web server of the interchange (101), with a set of parameters to indicate the amount (203), the identity of the merchant, a reference to the purchase, etc. Thus, the user does not have to provide any personal information to the server (113) of the merchant to complete the payment process.

Alternatively, the user may provide the phone number (123) to the merchant to process the payment. Thus, the user does not have to visit the web site of the interchange (101) to complete the payment.

FIG. 8 illustrates a user interface to initiate a payment request according to one embodiment, after the payment request is redirected to the web site of the interchange (101). In FIG. 8, the user interface (201) includes the identity of the merchant and the amount (203) of the requested payment. The user interface (201) includes a text field (183) to allow the user to provide the phone number (123) to identify the account information (121) via its association with the phone number (123) in the data storage facility (107).

Further, user authentication may be used to reduce false messages to the phone number (123). For example, the user interface (201) may request a PIN for enhanced security. For example, the user may be required to register with the interchange (101) prior to using the services of the interchange (101); and after registering with the interchange (101), the user is provided with the PIN or can created a customized PIN to access the functionality provided by the user interface (201).

Alternatively, the user interface (201) may request an identifier associated with the phone number (123) to initiate the payment transaction. In some embodiments, the user interface (201) requires the user to provide no information other than the phone number (123) in the text field (183) to initiate the transaction.

In FIG. 8, the user interface (201) allows the user to select one option from a plurality of payment options, including paying via the phone bill, and paying via one or more of the accounts identified by the account information (121) associated with the phone number (123) in the data storage facility (107).

In some embodiments, the user interface (201) may present the payment options after authenticating the user (e.g., via a personal identification number or password) for enhanced security.

In some embodiments, the user interface (201) identifies the different accounts represented by the account information (121) by showing aliases of the accounts. The aliases may be previously specified by the user, or be dynamically generated by the interchange (101) based on the types of the accounts and/or portions of the account information (121) (e.g., the first or last few digits of the account number)

In one embodiment, once the user submits the payment request via the user interface (201), the interchange (101) transmits a confirmation message to the mobile phone (117) according to the phone number (123) provided in the text field (183). In one embodiment, the interchange (101) transmits the confirmation to the mobile phone (117) after the user is authenticated via the user interface (201) to reduce the possibility of unauthorized/unwelcome messages to the mobile phone (117), which may occur when the user intentionally or unintentionally provides an unrelated phone number in the entry box (183).

FIG. 9 illustrates a user interface to confirm a payment request according to one embodiment. In FIG. 9, the confirmation message (217) includes the amount (203) of the requested payment and the identity of the payee (e.g., a merchant operating the server (113)).

In one embodiment, the confirmation message (217) includes the instruction to reply with a code, such as a code (e.g., “pay”) provided in the confirmation message (217) as illustrated in FIG. 9.

The presence of the code in the reply message is an indication of the user approving the request; and the requirement for such a code in the reply eliminates false confirmations (e.g., generated via accidental replies or automated replies).

Alternatively, or in combination, the requested code may include a PIN associated with the account, and/or a code (not shown) randomly generated and presented in the user interface used to initiate the payment transaction (e.g., user interface (201)).

In some embodiments, the code requested in the text message (217) may be a PIN associated with the phone number (123). The text message (217) does not include the code; and the knowledge of the code is an indication of the identity of the user. Thus, the use of such a code increases the security of the transaction.

In a further embodiment, the code requested in the text message (217) includes a code that is provided in response to the payment request (e.g., via the user interface (201), not shown in FIG. 9). The code may be generated randomly at the time the request is received via the user interface (201), or when the user interface (201) is presented to the user. The code provided to the user interface (201) can be requested in the reply received from the user interface (190) to indicate that the user who is in possession of the mobile phone (117) has actual knowledge about the payment request submitted via the user interface (201).

After the correct reply is received, the interchange (101) communicates with the account server (125) to electronically charge the user using the account information (121) and pays the payee using the funds collected via communicating with the account server (125). The interchange (101) then notifies the user when the payment transaction is complete.

For example, the interchange (101) may notify the user via a text message to the mobile phone (117), as illustrated in FIG. 10. FIG. 10 illustrates a user interface to confirm the completion of a payment transaction according to one embodiment. No reply to the message that confirms the completion of the payment transaction is necessary. Once the payment transaction is complete, the user would have access to the product purchased via the payment transaction.

In one embodiment, the interchange (101) stores an address of the user associated with the phone number (123). After the completion of the payment transaction, the interchange (101) provides the address to the server (113) of the merchant for the delivery of the purchased product. In some embodiments, the user may provide multiple addresses associated with the phone number (123) and may select one as a delivery address in the confirmation/approve message to the interchange (101). Alternatively, the interchange (101) may receive an address for product delivery from the mobile phone (117) together with the confirmation/approve message, and then forward the address to the server (113) of the merchant. Thus, the shipping address of the transaction is verified to be associated with the mobile phone (117). In alternative embodiments, the user may directly provide the shipping address in the website hosted on the server (113) of the merchant.

In other embodiments, the user is provided with the option to pay via the mobile phone bill associated with the phone number (123). The interchange (101) may dynamically calculate a set of premium messages, based on a set of limited number of predetermined prices for premium messages, to match the purchase price. The interchange (101) sends the set of premium messages to the mobile phone (117) at the phone number (123) to collect the funds via the telecommunication carriers to pay for the purchases. Thus, the purchase prices are not limited to the set of predetermined prices for premium messages. In some embodiments, the interchange (101) may send the set of premium messages within a period of time (e.g., a week, a month, a number of months, etc.) to spread the payments over the period of time (e.g., to overcome budget limits and/or limits imposed by regulations).

FIG. 11 illustrates a way to redirect a payment confirmation according to one embodiment. For example, after the user submits the payment request to the interchange (101) via the user interface (201) shown in FIG. 8, the interchange (101) may present the user interface (201) illustrated in FIG. 11 to the user. The user interface (201) indicates that the request is being processed; and the user interface (201) is periodically updated to show progress. Once the payment transaction is completed, the user interface (201) provides a confirmation message and may automatically redirect the user back to the website of the payee (e.g., to access the purchased products or services).

In one embodiment, the user is required to provide the approval in response to the confirmation message (217), as illustrated in FIG. 9, within a predetermined period of time. If the user fails to provide the approval from the mobile phone (117) within the predetermined period of time, the payment request may be rejected; and the user interface (201) may present a message indicating the failure and then redirect the user back to the website of the payee.

In some embodiments, instead of redirecting the user back to the website of the payee after the expiration of a predetermined period of time (e.g., after the failure of the payment process, or after the completion of the payment), the user interface (201) may provide a link to the website of the payee to allow the user to manually select the link to go back to the website of the payee to continue the process at the website of the payee.

FIG. 12 illustrates a user interface to receive payment options according to one embodiment. In FIG. 12, the interchange (101) sends a message (217) to the mobile phone (117) to provide a number of options to the user. The message (217) identifies the amount (203) of the requested payment and the identity of the payee (e.g., a merchant operating the server (113)) and asks the user to approve the payment request via a reply that contains a selected payment option.

In FIG. 12, the user may reply with the code “1” to approve the payment request and to pay via the phone bill of the mobile phone (117). Alternatively, the user may reply with credit card information to charge the payment to a credit card, as illustrated in FIG. 12.

In one embodiment, if the user provides credit card account information in the approval message, the credit card account information is stored and associated with the phone number (123) in the data storage facility (107). Thus, in subsequent approval messages, the user does not have to supply the same information again.

For example, the data storage facility (107) may store account information for each of a plurality of account types (e.g., Visa, MasterCard, checking, savings, etc.) Thus, each of the accounts can be identified to the user via the account type in the confirmation message, without revealing the details of the account information.

For example, the interchange (101) may combine the name of the financial institutions and the type of accounts to generate aliases for the account information.

In some embodiment, the user may define the aliases for the account information by supplying the aliases with the account information (121) for association with the phone number (123).

FIG. 13 shows a method to process an online payment according to one embodiment. In FIG. 13, the interchange (101) receives (301) an account identifier (e.g., 121) from a user and associates (303) the account identifier with a phone number (123) of the user in the data storage facility (107). Over the Internet the interchange (101) subsequently receives (305) a request for payment to be paid to a payee via the mobile phone (117) identified by the phone number (123). In response to the request, the interchange (101) transmits (307) a message (217) to the mobile phone (117) to confirm the payment.

After receiving (309) a confirmation or approval from the mobile phone (117) for the payment, the interchange (101) electronically charges (311) the user an amount using the account identifier (e.g., via communicating with the account server (125) using the account identifier). The interchange (101) then transfers (313) the amount to a payee to fulfill the payment.

FIG. 14 shows another method to facilitate a payment transaction according to one embodiment. In FIG. 14, the interchange (101) receives (331) a request to pay an amount to a payee via a mobile phone (117). The interchange (101) transmits (333) a message (217) to the mobile phone (117) to confirm the request via the converter (131) corresponding to the controller (115) of the mobile phone (117).

After the interchange (101) receives (335) a confirmation with an account identifier (e.g., 121) from the mobile phone (117) for the request, the interchange (101) electronically communicates (337) with a financial institution to charge the user the specified amount using the account identifier. The interchange (101) pays (339) the payee according to the amount, optionally charges (341) the user a first fee to pay the payee, and optionally charges (343) the payee a second fee for processing the payment.

In one embodiment, the users are given an incentive to provide the account information (121) for electronic payments via the account servers (125). For example, the interchange (101) may charge a lower fee for fulfilling payment requests via the account server (125) than for fulfilling payments requests via the phone bill. For example, the interchange (101) may offer rebates, discounts, etc. to the users who provide the account information (121). In some embodiments, the interchange (101) can complete a payment process via the account server (125) with fewer restrictions than via the phone bill.

In one embodiment, the merchant may specify the second fee. Different merchants may offer different percentages of the purchase prices as the second fee; and the interchange (101) may calculate the first fee based on the second fee offered by the merchant, by deducting the second fee from the total fees to be charged (e.g., fees charged by the telecommunication carrier for collecting the funds via the mobile phone bill associated with the phone number (123) and/or the fees charged by the interchange (101) for processing the payments). Since the first fee is charged to the customer (e.g., the purchaser of products and services), the cost to the customer can vary based on the selection of the merchant. For the same purchase prices, the first fee (and thus the cost to the customer) may be different for purchases made via different merchants, because the merchants may offer different percentages of the purchase price as the second fee. In some embodiments, the first and second fees include both fees charged by the telecommunication carrier for collecting the funds via the mobile phone bill/account associated with the phone number (123) and the fees charged by the interchange (101) for processing the payments. In some embodiments, the first fee includes the fees charged by the telecommunication carrier but not the fees charged by the interchange (101). In some embodiments, the second fee includes the fees charged by the telecommunication carrier but not the fees charged by the interchange (101). In some embodiments, the first fee and/or the second fee do not include the fees charged by the telecommunication carrier. In some embodiments, the first fee is not charged; and in other embodiments, the second fee is not charged.

FIGS. 15-18 show methods to approve a payment transaction according to some embodiments.

In FIG. 15, after the interchange (101) confirms (341) an identity of a user of a user terminal (111), the interchange (101) receives (343) from the user terminal (111) a request to pay via a phone number (123) of the user. In one embodiment, the interchange (101) confirms the identify of the user of the user terminal (111) and/or associates the identity of the user of the user terminal (111) with the phone number (123) of the mobile phone (117) prior to the user submitting a request to pay via the phone number (123). Thus, communications with the mobile phone (117) at the phone number (123) for the confirmation and/or approval of the request does not have to take place between the request and the payment operation; and thus the delay between the request and the payment operation can be reduced.

For example, the user terminal (111) may include a web browser; and the user may log into a web server of the interchange (101) using the web browser. The interchange (101) may prompt the user via the web browser running on the user terminal (111) to provide the phone number (123) and a password associated with the phone number (123). After verifying the password, the user is logged into a session tracked by the web browser on the user terminal (111); and the web browser running on the user terminal (111) is associated with the phone number (123).

In one embodiment, the interchange (101) further communicates with the mobile phone (117) at the phone number (123) to complete the verification process. For example, the interchange (101) may send a one-time verification code to the mobile phone (117) at the phone number (123) and request the user to provide the correct one-time verification code back via the user terminal (111) to verify the association between the user terminal (111) and the phone number (123). Alternatively, the interchange (101) may provide the one-time verification code to the user terminal (111) and instruct the user to communicate the code back to the interchange (101) via the mobile phone (117) at the phone number (123). Alternatively, after the user logs in using the user terminal (111), the interchange (101) may send a message to the mobile phone (117) to request a reply from the mobile phone (117) at the phone number (123) within a predetermined period of time to validate the session. In some embodiments, after the user provides the phone number (123) to the interchange (101) using the user terminal (111), the user is instructed to provide the password via the mobile phone (117) to complete the log in process.

In one embodiment, the user terminal (111) tracks the session. For example, the user terminal (111) may use a web browser to track the session via information maintained by the web browser (e.g., cookies). Alternatively, or in combination, the interchange (101) may track the session by maintaining information on the data storage facility (107). For example, after the user completes the log in process, the interchange (101) may identify the user terminal (111) via identifiers such as Internet address, Media Access Control address (MAC address), a different phone number (e.g., when the user terminal is a different mobile phone), or other software or hardware identification number associated with the user terminal (111), such as a digital certificate; and the interchange (101) may associate the phone number (123) with such identifiers until the expiration of a predetermined time period, or after the user signals an end of the session using the user terminal (111) or using the mobile phone (117) at the phone number (123). In one embodiment, the interchange (101) associates a plurality of identifiers of the user terminal (111) with the phone number (123) for the session. When at least one of the identifiers of the user terminal (111) is changed, the interchange (101) may terminate the session automatically.

In FIG. 15, after the user terminal (111) submits the request to pay via the phone number (123), the interchange (101) approves (345) the request based on the confirming of the identity of the user performed prior to the request and processes (347) the request using funds associated with the phone number (123). For example, the interchange (101) may transmit premium messages, via a corresponding converter (131), to a mobile phone (117) at the phone number (123) to collect the funds, or receive premium messages from a mobile phone (117) at the phone number (123) to collect the funds. For example, the interchange (101) may determine the account information (121) (e.g., an account identifier, such as a credit card number, a bank account number, a debit card number, etc.) stored and associated with the phone number (123) on the data storage facility (107) of the interchange (101) to charge the user using the account information (121).

In one embodiment, in response to the payment request from the user terminal (111), the interchange (101) may send a notification message to the mobile phone (117) at the phone number (123). The user is not required to provide a reply to complete the payment process. However, the user of the mobile phone (117) is provided with the option/opportunity to reply and report a fraudulent use, or to cancel the request (e.g., within a predetermined period of time).

In one embodiment, the data storage facility (107) stores a password associated with the phone number (123) for authentication. In FIG. 16, after the interchange (101) receives (351) a password and a phone number (123) from a user terminal (111), the interchange (101) determines (352) whether the received password is the correct password for the phone number (123). If the received password is the correct password for the phone number (123), the interchange (101) associates (353) the user terminal (111) with the phone number (123) in the data storage facility (107). If, during the time period in which the user terminal (111) is associated with the phone number (123), the interchange (101) receives (355) from the user terminal (111) a request to pay a payee (e.g., via the user interface (201) illustrated in FIG. 8), the interchange (101) may approve (357) the request based on the confirmed association between the user terminal (111) and the phone number (123) and pay the payee using funds associated with the phone number (123), without requiring a confirmation via the mobile phone (117) at the phone number (123). In some embodiments, after the user terminal (111) submits the phone number (123) to the interchange (101), the interchange (101) may request the password from the mobile phone (117) at the phone number (123).

In one embodiment, during the time period in which the user terminal (111) is associated with the phone number (123), the interchange (101) may automatically provide the phone number (123) in the text field (183) in the user interface (201) for submitting a payment request, as illustrated in the FIG. 8, based on the association between the user terminal (111) and the phone number (123). The phone number (123) can be provided by the interchange (101) in the text field (183) as a default input. Alternatively, the interchange (101) may not provide the phone number (123) and may require the user to enter the phone number (123) in the text field (183) for enhanced security. In some embodiments, the interchange (101) may dynamically determine whether or not to present the phone number (123) in the text field (183) based on a transaction pattern associated with the phone number (123). For example, if the current request matches the pattern, the interchange (101) presents the phone number (123) as the default input to simplify user interactions; otherwise, the interchange (101) does not provide the phone number (123) in the text field (183) for enhanced security.

In FIG. 17, after the interchange (101) receives (361) a phone number (123) from a user terminal (111), the interchange (101) communicates (363) with the user for an advance approval for the user terminal (111) via a mobile phone (117) at the phone number (123). For example, the interchange (101) may communicate with the mobile phone (117) at the phone number (123) for the advance approval and/or communicate with the user terminal (111) to confirm a password associated with the phone number (123).

In one embodiment, the advance approval is specific for the user terminal (111); and the interchange (101) stores identifiers of the user terminal (111) with the advance approval. For example, the interchange (101) may communicate with the user terminal (111) and/or the mobile phone (117) to associate the user terminal (111) with the phone number (123) for the advance approval of one or more subsequent payment requests.

In some embodiments, the advance approval is not limited to a particular user terminal (111). For example, the user may directly use the mobile phone (117) at the phone number (123) to communicate the advance approval to the interchange (101) without having to identify the user terminal (111). Alternatively, the user may use a particular user terminal (111) to initiate the communications with the interchange (101) for the advance approval without limiting the advance approval to subsequent payment requests from the same particular user terminal (111).

In one embodiment, the advance approval is associated with the phone number (123) on the data storage facility (107). When a request to pay via the funds associated with the phone number (123) is received, the advance approval associated with the phone number (123) is identified and applied by the interchange (101). The user does not have to explicitly identify the advance approval in making the payment request.

In one embodiment, the interchange (101) may assign an identification code for the advance approval for enhanced security. The user may use the identification code in the payment request to explicitly identify the advance approval.

In one embodiment, the advance approval specifies a time limit for the expiration of the approval, a budget amount for one or more payment requests, a limit on the types of permitted products and/or services, a time window for permissible payment requests, a frequency for permissible payment requests, and one or more limits based on certain characteristics of the payees (e.g., web addresses, countries, categories).

In one embodiment, the advance approval may specify some limits on the permissible user terminals (111). For example, the advance approval may limit the advance approval to user terminals located with certain geographic areas. The interchange (101) may determine the geographic areas of the user terminals (111) based on the IP addresses of the user terminals (111), the access points for wireless local area communications, the base stations for cellular communications, etc.

After the advanced approval is associated with the phone number (123), the interchange (101) may receive (365) from the user terminal (111) a request to pay a payee via the phone number (123). Based on the advance approval the interchange (101) may approve (367) the request and pay (369) the payee using funds associated with the phone number (123), without requiring a confirmation message from the user via communications with the mobile phone (117) at the phone number (123).

In some embodiments, the interchange (101) may use the transaction history (127) to determine whether or not to require a confirmation message from the user via communications with the mobile phone (117) at the phone number (123). The transaction history (127) may include a number of records of prior confirmed/approved payment requests.

For example, based on the records of prior payment requests the interchange (101) may determine a payment pattern for the phone number (123), such as a list of frequently used user terminals (111) for the phone number (123), a range for typical payment amounts, a time of day within which typical payment requests are received for the phone number (123), a list of frequently used payees paid via the phone number (123), a list of categories of services and/or products frequently paid for via the phone number (123), a recent payment request confirmed within a predetermined period of time, etc.

In FIG. 18, the interchange (101) processes (371) a plurality of requests to pay via a phone number (123). The interchange (101) processes (371) the requests via communicating with the mobile phone (117) at the phone number (123). For example, the interchange (101) may send a message to the mobile phone (117) at the phone number (123) and request a reply to the message from the mobile phone (117). For example, the interchange (101) may request a PIN from the mobile phone (117) at the phone number (123) to confirm the requests. For example, the interchange (101) may send one-time codes representing the requests to the mobile phone (117) or receive one-time codes representing the requests from the mobile phone (117).

The interchange (101) stores (373) transaction records of the payment requests and determines (375) a pattern of the payment requests.

Subsequently, when the interchange (101) receives (377) from a user terminal (111) a request to pay a payee via the phone number (123), the interchange (101) determines (378) whether the request matches the pattern. If the request matches the pattern, the interchange (101) pays (379) the payee using funds associated with the phone number (123), without requiring a confirmation communicated via the mobile phone (117) at the phone number (123) to speed up the payment process. The interchange (101) may send a notification to the mobile phone (117) at the phone number (123), without requiring a reply prior to making the payment.

In one embodiment, after the interchange (101) transmits a premium message to the mobile phone (117) for a transaction between the user of the mobile phone (117) and the merchant of the server (113), the telecommunication carrier of the mobile phone (117) sends a bill to the user of the mobile phone (117) for the premium message (e.g., on a monthly statement date) and requests the user to pay the bill within a number of days (e.g., on a due date specified on the monthly statement). The user may pay the bill before or on the due date, or dispute the charge, or fail to pay the bill for various reasons. If the user pays the bill, including the charge for the premium message, the telecommunication carrier may keep a portion of the total amount charged via the premium message and provide the remaining portion to the interchange (101). After the telecommunication carrier provides to the interchange (101) the funds collected via the premium message, the interchange (101) pays the merchant of the server (113) to close the transaction at the server (113).

For example, the telecommunication carrier may bill the user of the mobile phone (117) monthly and settle with the interchange (101) monthly. The interchange (101) may settle with the merchant of the server (113) monthly, after settling with the telecommunication carrier. Thus, it may take several months before funds charged via the premium message reaches the merchant.

In one embodiment, to accelerate the transaction process, the interchange (101) notifies the server (117) of the merchant when the premium message is sent to the mobile phone (117), allowing the server (117) to release the purchased item to the user. Thus, the user does not have to wait until the funds reach the merchant to access the purchased item. Further, the interchange (101) may offer to provide an amount to the merchant, before the funds collected via the premium message become available.

For example, the interchange (101) may provide advance payments to the merchant (e.g., on a monthly basis) based on the collection of transaction information and risk analysis. The interchange (101) can prepare an estimate of an amount the merchant is likely to earn, based on the data collected in a transaction database. The interchange (101) then notifies the merchant of the estimated amount and offers to deliver the estimated amount to the merchant prior to receiving funds from the telecommunication carrier. Upon receipt of payments from the telecommunication carrier, the interchange (101) compares the actual receipts with the amount prepaid to the merchant to generate a balance to properly settle with the merchant, taking into account any refunds, charge backs, fee changes and other variables.

In one embodiment, the interchange (101) charges the merchant a variable fee for the advance payment, based on the volume and duration of time of the advance payment and other considerations, such as repayment risk, credit worthiness, etc. In one embodiment, the interchange (101) may present the transaction information and risk analysis results to a third party lender to allow the merchant to borrow against the income expected from the premium messages sent by the interchange (101).

FIG. 19 illustrates a transaction database according to one embodiment. The transaction database (401) may be maintained by the interchange (101) in the data storage facility (107). In FIG. 19, the transaction database (401) includes a number of records (e.g., 410) for transactions between users of mobile phones (e.g., 117) and servers (e.g., 113) of merchants.

In one embodiment, a transaction record (410) includes a number of fields, such as transaction ID (402) to identify a transaction, merchant ID (403) to identify the merchant, phone number (123) to identify the user to whom the premium message is sent, IP address (405) of the user terminal (111) used to initiate the transaction, type (406) of the item purchased, sales amount (407), refund (409) which (if any) occurred after settling the payments for the transaction, etc.

In one embodiment, the transaction record includes not only fields for the identification of the transaction but also fields for the identification of various characteristics of the transaction, which can be used to estimate the risk in the settlement of the transaction and/or the risk in similar transactions. More or less fields can be used in different embodiments. For example, the transaction record may include a field to record the length of the time period (e.g., numbers of days) between when a transaction occurs and when funds collected via the premium messages are received for the transaction from the telecommunication carrier of the mobile phone (117). For example, the transaction record may include a field to record whether or not the user of the mobile phone (117) disputes the transaction, or requests a refund for the transaction.

Based on past transactions that have been settled, the interchange (101) can estimate the risk in the transactions that have payments pending to be settled. For example, based on the settled transactions, the interchange (101) can compute the ratio between the amount actually collected via premium messages sent on behalf of the server (113) of a merchant and the amount initially charged via the premium messages sent on behalf of the server (113) of a merchant. For example, based on the settled transactions, the interchange (101) can compute the rate at which the user at the phone number (123) pays for the premium messages received from the interchange (101). For example, based on transaction statistics, the interchange (101) can compute the rate at which users request refunds for purchasing items having the type (406). For example, based on the settled transactions, the interchange (101) can compute the likelihood of fraudulent purchases made at the IP address (405).

The risks may be a function of various parameters of the transaction, the user and/or the merchant. For example, the age of the user can be a factor, since the purchases made by children may be disputed by their parents. For example, the servers configured to provide products or services for children may have a high rate of refund requests or charge backs.

Based on the risk analysis performed using information about the settled transactions, the interchange (101) can compute an amount the merchant is expected to receive for a set of transactions in which the interchange (101) has sent premium messages to mobile phones on behalf of the merchant and the interchange (101) has not yet received from the corresponding telecommunication carriers any indication about whether the users have paid for the premium messages.

In one embodiment, the interchange (101) computes the amount on a transaction by transaction basis. For example, for each of the pending transactions (e.g., not yet settled transactions), the interchange can determine the probability of the successful collection of funds from the premium messages sent in the transaction and compute an expected amount based on the probability and the sales amount (407). The expected amounts of pending transactions for a merchant can be summed to generate the expected amount that can be offered to the merchant for pending transactions (e.g., on a monthly basis).

Alternatively, the interchange (101) can group transactions by characteristics and compute the expected amount based on the risk of the group. For example, the ratio between the actual amount collected in the past for the merchant and the amount initially charged on behalf of the merchant in the past can be applied to the total amount charged on behalf of the merchant in the pending transactions to obtain an estimated amount the merchant can expect.

In some embodiments, the interchange (101) provides the risk data for the pending transactions to a lender to allow the lender to make loan offers to the merchant. When the interchange (101) receives the payments from the telecommunication carries for the premium messages, the interchange (101) can repay the lender using the funds collected on behalf of the merchant.

In one embodiment, the interchange (101) may identify the transactions that have a probability of being a fraudulent transaction higher than a threshold and exclude the transactions from advance payment offers. For example, when a user terminal (111) at a single IP address is responsible for initiating purchase requests charged to multiple different mobile phones (117) (e.g., more than two) within a predetermined period of time (e.g., two hours), there is a high likelihood that some or all of the transactions are fraudulent. Thus, the interchange (101) may not offer any advance payment to the merchant for such transactions (or a low percentage of the amount charged, based on the likelihood of the transaction being a fraudulent transaction).

FIG. 20 shows an arrangement to accelerate payments to a merchant according to one embodiment. In FIG. 20, the user terminal (111) submits a purchase request (177) to the server (113) of a merchant. The purchase request (177) includes a phone number (123) of the mobile phone (117) of the user. The server (113) of the merchant submits a charge request (179) to the interchange (101) to charge the user using the phone number (123). In some embodiments, the user terminal (111) may send the charge request directly to the interchange (101), with an indication of the merchant server (113) identified as the payee.

In one embodiment, the interchange (101) communicates with the mobile phone (117) and/or the user terminal (111) to confirm the charge request (179). For example, the interchange (101) may transmit a text message to the mobile phone (117) and request a reply from the mobile phone (117) to confirm the charge request (179).

After the charge request (179) is confirmed, the interchange (101) sends one or more premium messages (411) to the mobile phone (117) to cause the telecommunication carrier to collect funds corresponding to the prices of the premium message (411) (e.g., via mobile terminated premium messages). In alternative embodiments, the interchange (101) may receive premium messages (411) from the mobile phone (117) to collect the funds (e.g., via mobile originated premium messages). In other embodiments, the interchange (101) may communicate with the controller (115) of the mobile phone (117) to charge an amount on the phone bill of the mobile phone (117) without the transmission of a premium message to or from the mobile phone (117) (e.g., via operator billing).

In FIG. 20, after the interchange (101) transmits the premium message (411) to the mobile phone (117), the interchange (101) provides a notification (413) to the merchant server (113) to allow the server (113) of the merchant to deliver (415) the item purchased by the user terminal. For example, the item purchased may be a song, a video clip, an article, a number of points usable to play games on the server (113), or an amount of virtual cash that can be used on the server (113) to access premium features. Thus, the user may access the purchased item shortly after the transmission of the premium message, without having to wait until the funds are collected by the controller (115) and passed on to the merchant (e.g., via the interchange (101)).

In FIG. 20, the interchange (101) may provide the funds (417) to the merchant server (113) before the controller (115) obtains the funds charged via the premium message (411). The interchange (101) may estimate the risk in the transaction and provide only a portion of the total balance of the transaction that is due to the merchant. When the risk is low, the interchange (101) may provide the entire amount that is due to the merchant. In some embodiments, the interchange (101) may provide the funds (417) before, or concurrently with, the notification (413) (e.g., via electronic payments). Alternatively, the interchange (101) may provide the funds via monthly settlements with the merchant. In further embodiments, the merchant can access the interchange (101) (e.g., via a web interface) to request a list of pending transactions, view the estimated amount that can be generated from the pending transactions, and request an advance payment. Thus, the closing and settlement of the transaction from the point of view of the merchant can be accelerated.

In FIG. 20, after the controller (115) bills the mobile phone (117) for the premium message (411) and receives the payments (419), the interchange (101) receives funds from the controller (115). The interchange (101) reconciles (423) the funds (417) advanced to the server (113) and the funds (421) actually received from the controller (115) to generate a balance. According to the balance, the interchange (101) may send additional funds to the merchant, or reduce future advance payments to the merchant, or request a refund from the merchant. In one embodiment, the interchange (101) further adjusts the risk assessments to reduce the subsequent balance generated from the mismatch between the advanced funds (417) and the actual collected funds (421).

FIG. 21 shows a system to provide funds to a merchant according to one embodiment. In FIG. 21, a third party lender (431) is used to finance the advance payment to the merchant of the server (113), where the advance payment is secured or backed by the premium messages (411) sent to the mobile phone (117) for the purchase request (177) submitted from the user terminal (111).

In FIG. 21, the interchange (101) communicates with the mobile phone (117) for a confirmation (173) of the charge request (179) received from the server (113). The confirmation (173) reduces errors and fraudulent transactions. The interchange (101) uses the transaction database (401) hosted on the data storage facility (107) to estimate the probability of success in collecting the funds as priced by the premium messages from the user of the mobile phone (117).

In one embodiment, the interchange (101) provides the risk estimation (433) to the lender (431) to allow the lender (431) to make a loan to prepay the merchant of the server (113) for the transaction. The interchange (101) collects the funds via the premium message (411) to repay the loan on behalf of the merchant and settles with the merchant and the lender (431) at the end of the term of the loan.

In some embodiments, the merchant of the server (113) can sell the revenue generated by the transaction to the lender (431). After the interchange (101) presents the risk estimation (433) to the lender (431) and the merchant, the lender may purchase from the merchant the rights to the revenue generated by the premium message (411). The lender (431) provides the funds (417) as the payment for the rights to the revenue generated by the premium message (411). Thus, the transaction can be closed and settled at the server (113) upon receiving the funds (417) from the lender (431). When the interchange (101) obtains the funds collected by the telecommunication carrier of the mobile phone (117), the interchange (101) provides to the lender (431) the actual revenue generated by the premium message (411).

In some embodiments, the interchange (101) allows the lender (431) to access the transaction database (401) to estimate risk and determine the price to purchase the rights to the revenue generated by the premium message (411) sent to the mobile phone (117).

In some embodiments, the interchange (101) purchases the rights from the merchant server (113) or makes the loan to the merchant, based on an analysis of the transaction database (401). For example, in response to the charge request, the interchange (101) may offer to buy the rights to the payment to accelerate the closing of the transaction at the server (113).

FIG. 22 shows a method to provide funds to a merchant according to one embodiment. In FIG. 22, an interchange (101) is configured to store (451), in a transaction database (401) hosted on a data storage facility (107), information about first transactions that are billed via first premium messages and that have been settled. The interchange (101) is configured to transmit (453) second premium messages to bill for second transactions on behalf of a merchant. To prepay the merchant, the interchange (101) is configured to identify (455) an amount of funds that are expected to be collected successfully via the second premium messages, based on the stored information about the first transactions. The identified amount is typically a portion of the total amount billed via the second premium messages.

In one embodiment, the interchange (101) prepays the merchant the identified amount of funds for the second transactions, before the funds collected via the second premium messages are received from the telecommunication carrier(s) of the mobile phones (e.g., 117) that receive the second premium messages. After the funds collected via the second premium messages become available, the interchange (101) compares the amount of the actual collected funds and the prepaid amount to further settle with the merchant.

In one embodiment, the interchange (101) prepays the merchant the identified amount of funds as a loan that is backed up by the second transactions. The interchange (101) may charge the merchant fees and/or interest for the loan, based on the size of the loan and/or the duration of the loan. After the funds collected via the second premium messages become available, the interchange (101) applies the funds toward the repayment of the loan. At the end of the predetermined term of the loan, the interchange (101) further settles with the merchant to clear the loan and/or the transaction balance.

In one embodiment, the interchange (101) prepays the merchant the identified amount of funds to purchase the rights to the revenues generated from the second premium messages. Thus, the identified amount of funds paid to the merchant settles the transactions at the server (113) of the merchant; and the interchange (101) can keep the actual funds subsequently collected via the second premium messages (e.g., 411).

In some embodiments, a third party lender (431) prepays the merchant the amount identified by the interchange (101), as a loan or as a purchase of the rights to the revenue generated from the second premium messages (e.g., 411).

In one embodiment, the prepaid amount is identified by the interchange (101) via determining a ratio between an amount collected via the first premium messages and an amount charged via the first premium messages. The first premium messages may be transmitted to collect payments on behalf of the same merchant, or one or more merchants selling items in a same category as the merchant.

In one embodiment, the interchange (101) is configured to identifying third premium messages that have been transmitted to different phone numbers based on purchase requests received from a single Internet Protocol (IP) address within a predetermined period of time. When at least one of the third premium messages is transmitted as part of the second premium messages on behalf of the merchant, the funds charged via the at least one of the third premium messages are excluded from the amount identified by the interchange (101).

In one embodiment, the amount identified by the interchange (101) is based at least in part on the payment histories of users who receive the second premium messages.

In one embodiment, the amount identified by the interchange (101) is based at least in part on the ages of the users who receive the second premium messages. For example, when the users are below a predetermined age limit, the users may not be authorized to make purchases (e.g., by their parents or guardians); and the transactions may be disputed. Thus, transactions by such users may have a lower rate of getting paid than transactions by other users.

In one embodiment, the interchange (101) is configured to identify, from the second premium messages, third premium messages that have a risk of not being paid for higher than a predetermined threshold and exclude the funds charged via the third premium messages from the amount identified for prepayment.

In one embodiment, to identify the amount for prepayment the interchange (101) estimates a risk of a third premium message of the second premium messages not being paid for, based on statistical data and one or more characteristics of a transaction associated with the third premium message, such as an Internet Protocol (IP) address used to initiate the transaction, a type of an item purchased in the transaction, a telecommunication carrier of a phone number to which the third premium message is transmitted, and/or the age of a user receiving the third premium message.

In one embodiment, to identify the amount to prepay the merchant, the interchange (101) determines success rates in collecting funds via premium messages as functions of a number of transaction characteristics, such as the characteristics of the users who made the purchase, the characteristics of the items purchased, the characteristics of the merchant, etc.

In one embodiment, the interchange (101) is configured to use various information to determine whether there is already sufficient data indicating the user approval to proceed with billing the user for making a payment using funds associated with the phone number (123) of the user. When there is sufficient data indicating the user approval, the interchange (101) is to skip the operations, performed via communications with the mobile phone of the user at the phone number (123), to request explicit user authorization/confirmation for the billing operations.

In one embodiment, after the interchange (101) receives the phone number (123) of the user in a request to pay a merchant using funds associated with the phone number (123), the interchange (101) is configured to communicate with the mobile phone (117) at the phone number (123) to request explicit confirmation of the payment request and/or the authorization to bill the user. The interchange (101) may bill the user to collect funds for the payment transaction via the phone bill of the phone number (123), a credit, debit or prepaid account associated with the phone number (123) in the data storage facility (107), or other funding sources, such as a stored value account or a payment intermediary account associated with the phone number (123).

In one embodiment, during the determination of whether to skip the explicit confirmation/authentication operations, the interchange (101) is configured to determine whether it is permissible to skip the mobile communications for the explicit confirmation/authorization, determine whether it is feasible to perform the mobile communications for the explicit confirmation/authorization for the current payment transaction, and determine whether the risk associated with skipping the explicit confirmation/authorization is lower than a threshold.

If the communication with the mobile phone (117) at the phone number (123) for the explicit confirmation/authorization can be skipped, the delay caused by the mobile communications can be eliminated. Thus, from the point of view of the merchant and the user, the processing of the payment transaction is accelerated. Further, the user has less input to provide than the user would have to if the explicit confirmation/authorization is required; and thus the user experience is improved. Further, when the mobile communications for the explicit confirmation/authorization is skipped, the payment transaction can be processed promptly even in the presence of a network outage in the wireless telecommunications network.

In one embodiment, the interchange (101) is to skip the explicit confirmation/authorization, made via communicating with the mobile phone (117) at the phone number (123), after data has been collected to have sufficient confidence in the assertion that the user of the phone number (123) has provided approval to proceed with billing a funding source associated with the phone number (123) of the user.

In one embodiment, the interchange (101) is configured to evaluate the risk of the payment transaction based on historic payment transactions processed by the interchange (101) and/or other information, such as credit and reputation information about the user, the phone number (123) and/or the device associated with the phone number (123). When the risk is higher than a threshold, the interchange (101) does not skip the explicit confirmation/authorization that is to be made via communicating with the mobile phone (117) at the phone number (123).

In one embodiment, the interchange (101) is to use real-time data to determine whether it is permissible and/or feasible to skip the mobile communications for the explicit confirmation/authorization, and use real-time data and historical data to determine whether the interchange (101) should skip the operations for explicit confirmation/authorization.

In one embodiment, the real-time data is generated with or after the receiving of the request for the payment transaction. In one embodiment, the real-time data is received in the interchange (101) (and the data storage facility (107)) with or after the request for the payment transaction. Examples of the real-time data include the time, date, physical location, merchant, transaction amount of the payment transaction, the type of the point of sales (POS) terminal initiated the transaction, the current status of the wireless telecommunication network (105), an identifier of the device used by the user to request the payment transaction, an identifier of the user making the request for the payment transaction, etc.

In one embodiment, the historical data is accessible to, or stored in, the interchange (101) (e.g., the data storage facility (107)) prior to the request for the payment transaction.

In one embodiment, the interchange (101) analyzes the real-time data and the historical data to predictively authenticate payment transactions, initiated from a mobile device, online computer, or point-of-sale terminal to use any combination of funding sources (e.g., mobile billing, credit/debit card, Automated Clearing House (ACH)) associated with the phone number (123) to make a payment. The predictive authentication is used to safely enhance the consumer purchase experience by instantly authenticating payment transactions without requiring additional action or input from the mobile phone (117) of the user.

In one embodiment, the interchange (101) makes decisions about whether to skip the explicit confirmation/authentication based on data available at the time the transaction is initiated, which can be received as input in real-time (e.g., from the server of the merchant, and/or a trusted third party) and/or gathered from existing data in the system (e.g., retrieved from the data storage facility (107) of the interchange (101)). After gathering the real-time and historical data upon the initialization of the payment transaction, the interchange (101) is to determine whether the explicit confirmation/authentication is required. If the confirmation/authentication operations are required (e.g., based on the rules, laws, user preferences, or based on a risk analysis which indicates that it is not safe to skip the operations), the interchange (101) is to prompt the user for authentication via communications with the mobile phone (117) at the phone number (123); otherwise, the interchange (101) skips the prompt and proceeds directly with the operations to bill the user.

FIG. 23 shows a system to simplify and accelerate payment processing according to one embodiment. In FIG. 23, the interchange (101) is configured to receive a charge request from the merchant server (113) (directly, or indirectly via the browser of the user of the mobile phone (117)).

In one embodiment, the interchange (101) uses various information to determine whether to skip the explicit confirmation/authentication performed through transmitting, to the mobile phone (117) at the phone number (123) of the user, a confirmation request and/or receiving, from the mobile phone (117), a confirmation reply.

In one embodiment, the data storage facility (107) stores various information, such as an identifier (512) of the user of the phone number (123), the history of payment transactions made via the phone number (123) stored in the transaction database (401), data (157) about the funding source(s) associated with the phone number (123), one or more identifiers (513) of devices used by the user to request the payment transactions, data (511) from a trusted third party, social graph data (514) about the user, user preference data (516), and regulatory data (515), such as applicable rules, regulations and laws related to the payment transaction. In one embodiment, the data storage facility (107) further stores collected real-time data, such as the time, date, physical location, merchant, transaction amount of the payment transaction, and the type of the point of sales (POS) terminal initiated the transaction.

In one embodiment, some of the data, such as data (511) from a trusted third party is received in the interchange (101) from the third party after the charge request is received; and the interchange (101) may or may not store the received real-time data in the data storage facility.

In one embodiment, the identifier (512) of the user used to identify the user involved in the charge request is the phone number (123), a user account identifier with the merchant (or the interchange (101)), an email address of the user, etc. In one embodiment, the identifier (512) of the user is used to extract further information about the user to determine the preference data (516) of the user, the local regulatory data (515) applicable to the user, and/or the creditworthiness information of the user (e.g., the third party data (511)).

In one embodiment, the interchange (101) is to retrieve, from the transaction database (401) hosted in the data storage facility (107), the data recording the prior transactions processed for the user identified by the identifier (512) of the user, including records of successful transactions, failed transactions, total amount requested, total amount spent, transaction frequency, transaction patterns, etc. The interchange (101) uses the transaction history to build a risk profile for the user. The risk profile is then used to determine the risk of the current payment transaction.

In one embodiment, the interchange (101) is configured to bill the user using a combination of funding sources to make a payment in accordance with a request or preference from the user. Examples of the funding sources include mobile billing, credit/debit card, ACH, prepaid cards, third party payment systems, etc.

In one embodiment, a user may use multiple devices to request the interchange (101) to process various payment transactions. The interchange (101) uses unique identifiers of the devices to separately identify the individual devices, such as mobile phones, tablets, laptop or desktop computers, point-of-sale terminals, etc. In one embodiment, the interchange (101) is configured to build a separate risk profile for each of the devices used by the user of the phone number (123) to improve the accuracy of risk evaluation. In response to the charge request from the merchant (or the user), received via the current device used by the user, the interchange (101) is configured to use the risk profile associated with the current device to evaluate the risk of the current payment transaction.

In one embodiment, various data (511) from trusted third parties, such as merchants, vendors, etc. are used to assist in risk analysis. Examples of such data include the merchant consumer ID, merchant consumer profile information (e.g., signup date, date of birth, purchase history, risk score, credit score, etc.), mobile phone number, verified mobile phone number, email address, Open ID, government-issued ID, social ID, etc. The third party data (511) can be passed into the interchange (101) in real-time (e.g., in response to the payment request) and/or asynchronously.

In one embodiment, the interchange (101) is further configured to use data (514) linked to the social graph of the user of the phone number (123), such as friends, social credit score, known network affiliations, social activity history/frequency. In one embodiment, the social graph data (514) is used in risk estimation (e.g., via determination of creditworthiness of the user).

In one embodiment, the interchange (101) provides a preference option to allow the user to explicitly opt-in to the convenience feature of skipping the mobile confirmation/authentication for payment requests. In one embodiment, after the user selects the preference option to opt-in to the convenience feature of skipping the mobile confirmation/authentication for payment requests, the interchange (101) is configured to communicate with the mobile phone (117) at the phone number (123) to confirm the selection of the option.

For example, the interchange (101) is configured to transmit a text message to the mobile phone (117) to request the user to confirm the selection of the option via replying to the text message.

Alternatively, in response to the user selecting the option via a web interface, a confirmation code is provided to the user via the web interface; and the user is prompted to transmit the confirmation code to the interchange (101) via a text message from the mobile phone (117) at the phone number (123) to confirm the selection of the option.

Alternatively, in response to the user selecting the option via a web interface, a confirmation code is provided to the mobile phone (117) at the phone number (123) via a text message; and the user is prompted to provide the confirmation code back to the interchange (101) via the web interface.

FIG. 24 shows a method to simplify and accelerate payment processing according to one embodiment. In FIG. 24, the interchange (101) is configured to receive (521) a phone number (123) to initiate a payment using funds associated with the phone number (123). Upon the initialization of the payment transaction, the interchange (101) is to determine (523) whether or not to skip the operations of mobile authentication of the payment request. If the interchange (101) determines not to skip the mobile authentication of the payment request, the interchange (101) is to communicate (525) with a mobile phone (117) at the phone number (123) to authenticate the payment request.

In one embodiment, the communicating (525) with the mobile phone (117) to authenticate the payment request includes transmitting a message to the mobile phone (117) at the phone number (123) and/or receiving a message from the mobile phone (117) at the phone number (123).

For example, in one embodiment, the communicating (525) with the mobile phone (117) to authenticate the payment request includes a round trip text message to the mobile phone (117) to request confirmation and back from the mobile phone (117) as a confirmation reply.

For example, in one embodiment, the communicating (525) with the mobile phone (117) to authenticate the payment request includes transmitting a confirmation code to the mobile phone (117) at the phone number (123) using SMS, and prompting the user to provide the confirmation code back to the interchange (101) using the device that initiated the payment transaction.

For example, in one embodiment, the communicating (525) with the mobile phone (117) to authenticate the payment request includes presenting a confirmation code to the device that initiated the payment transaction (e.g., as a response to the charge request), and prompting the user to provide the confirmation code back to the interchange (101) from the mobile phone (117) via SMS.

If the interchange (101) determines to skip the mobile authentication of the payment request, or after the communicating (525) with the mobile phone (117) to authenticate the payment request, the interchange (101) is to bill (527) the user using a funding source associated with the phone number (123) and then settle (529) the payment transaction with the funding source and the merchant.

In one embodiment, to bill the user, the interchange (101) is configured to transmit one or more premium messages to the mobile phone (117) at the phone number (123) to collect funds via a telecommunication carrier of the phone number (123). In another embodiment, to bill the user, the interchange (101) is configured to charge a bank account associated with the phone number (123), such as a credit account, a debit account, a prepaid account, a checking account, or a savings account.

In one embodiment, the determination (523) is based on historical transaction data, associated with the phone number (123) and retrieved from the transaction database (401) hosted in the data storage facility (107) of the interchange (101), and information associated with the request, such as the identifier (512) of the user, the identifier (513) of the device used by the user to make the payment request, social graph data (514) of the user, and/or the third party data (511).

In one embodiment, the interchange (101) is configured to provide a user interface to allow the user to select a preference option to skip the mobile communications. The interchange (101) stores the preference option (516) selected by the user with the phone number (123) after the user selects the preference option (516). In one embodiment, the interchange (101) is to determine the skipping of the mobile authentication operations if the preference option (516) is selected by the user; otherwise, the interchange (101) is not to skip the mobile authentication operations.

In one embodiment, the interchange (101) is configured to communicate with the mobile phone (117) to confirm the selection of the preference option (516) in response to the user selecting the preference option (516).

In one embodiment, the determination (523) of whether to skip the mobile communications is based on a risk of skipping the mobile communications and the requirements of regulatory rules, in addition to the preference data (516).

In one embodiment, the determination (523) of whether to skip the mobile communications is based on at least one identifier of the user and at least one identifier of a device of the user. In one embodiment, the one identifier of the user and the one identifier of the device of the user are used to identify a risk profile generated based on past payment transactions made using the current device of the user.

In one embodiment, the determination (523) of whether to skip the mobile communications is based on a type of the funding source for the payment. In one embodiment, a risk threshold associated with the type of the funding source for the settlement of the current payment transaction is used in the risk analysis.

In one embodiment, the determination (523) of whether to skip the mobile communications is based on information about the user received from the merchant in connection with the request. For example, in the embodiment, the merchant stores the phone number (123) of the user and/or the social graph data (514) of the user, which is provided to the interchange (101) in connection with the charge request of the payment transaction.

FIG. 25 illustrates a method to selectively skip authorization for mobile transactions according to one embodiment. In FIG. 25, the interchange (101) is configured to present (532) a user interface to receive a user selection for a preference to skip authentication performed via mobile communications with a mobile phone (117) at a phone number (123). For example, an option can be provided via a checkbox (or another user interface element) presented in a web page displayed in a browser of the user, or via a mobile application running on the mobile phone (117).

After the user selects the option, the interchange (101) determines (534) whether or not mobile confirmation of the preference is required (e.g., based on regulatory rules (515)). If mobile confirmation is required, the interchange (101) communicates (538) with the mobile phone (117) to confirm the user selection of the preference, before storing (536) the user selected preference about the convenience feature of skipping authentication.

In one embodiment, the stored preference is used during the processing of a payment request of the phone number (123).

In FIG. 25, after the interchange (101) receives (531) a request to process a payment to a merchant using funds associated with the phone number (123), the interchange (101) determines whether the local rules and laws governing the phone number (123), or the mobile phone (117), require the authentication operations. If the authentication is mandatory, or if the interchange (101) determines (535) that the user has selected the preference data (516) to require authentication, the interchange (101) is to communicate (541) with the mobile phone (117) to confirm the payment request, if (539) it is feasible to perform the mobile phone based authentication within a predetermined period of time.

In FIG. 25, if the interchange (101) determines that skipping authentication is permitted by rules and laws and user preferences, the interchange (101) further determines whether (537) the risk of the current payment transaction is high or low and whether (539) it is feasible to perform mobile authentication for the current payment transaction. In one embodiment, the interchange (101) determines the feasibility based on the current status of the wireless telecommunications network (105), the availability of a wireless connection to the mobile phone (117) at the phone number (123), etc.

If the risk of the present payment transaction is classified as low, the interchange (101) is to skip the communications designed for the authentication of the payment request and bill (543) the user using a funding source associated with the phone number (123).

If it is not feasible to perform the mobile confirmation/authentication of the payment request but the confirmation/authentication operations are required, preferred, and/or desirable, the interchange (101) may inform the merchant of the failure to process the payment transaction, prompt the user to use an alternative payment option, and/or prompt the user to change the preference data (516).

FIG. 26 shows a data processing system, which can be used in various embodiments. While FIG. 26 illustrates various components of a computer system, it is not intended to represent any particular architecture or manner of interconnecting the components. Some embodiments may use other systems that have fewer or more components than those shown in FIG. 26.

In one embodiment, each of the interchange (101), the data storage facility (107), the controllers (115), the mobile phones (117), the user terminals (111), the account server (125), and the servers (113) can be implemented as a data processing system, with fewer or more components, as illustrated in FIG. 26.

In FIG. 26, the data processing system (501) includes an inter-connect (502) (e.g., bus and system core logic), which interconnects a microprocessor(s) (503) and memory (508). The microprocessor (503) is coupled to cache memory (504) in the example of FIG. 26.

The inter-connect (502) interconnects the microprocessor(s) (503) and the memory (508) together and also interconnects them to a display controller, display device (507), and to peripheral devices such as input/output (I/O) devices (505) through an input/output controller(s) (506).

Typical I/O devices include mice, keyboards, modems, network interfaces, printers, scanners, video cameras and other devices which are well known in the art. In some embodiments, when the data processing system is a server system, some of the I/O devices, such as printer, scanner, mice, and/or keyboards, are optional.

The inter-connect (502) may include one or more buses connected to one another through various bridges, controllers and/or adapters. In one embodiment, the I/O controller (506) includes a USB (Universal Serial Bus) adapter for controlling USB peripherals, and/or an IEEE-1394 bus adapter for controlling IEEE-1394 peripherals.

The memory (508) may include ROM (Read Only Memory), volatile RAM (Random Access Memory), and non-volatile memory, such as hard drive, flash memory, etc.

Volatile RAM is typically implemented as dynamic RAM (DRAM) which requires power continually in order to refresh or maintain the data in the memory. Non-volatile memory is typically a magnetic hard drive, a magnetic optical drive, an optical drive (e.g., a DVD RAM), or other type of memory system which maintains data even after power is removed from the system. The non-volatile memory may also be a random access memory.

The non-volatile memory can be a local device coupled directly to the rest of the components in the data processing system. A non-volatile memory that is remote from the system, such as a network storage device coupled to the data processing system through a network interface such as a modem or Ethernet interface, can also be used.

In this description, various functions and operations may be described as being performed by or caused by software code to simplify description. However, those skilled in the art will recognize that what is meant by such expressions is that the functions result from execution of the code/instructions by a processor, such as a microprocessor. Alternatively, or in combination, the functions and operations can be implemented using special purpose circuitry, with or without software instructions, such as using Application-Specific Integrated Circuit (ASIC) or Field-Programmable Gate Array (FPGA). Embodiments can be implemented using hardwired circuitry without software instructions, or in combination with software instructions. Thus, the techniques are limited neither to any specific combination of hardware circuitry and software, nor to any particular source for the instructions executed by the data processing system.

While some embodiments can be implemented in fully functioning computers and computer systems, various embodiments are capable of being distributed as a computing product in a variety of forms and are capable of being applied regardless of the particular type of machine or computer-readable media used to actually effect the distribution.

At least some aspects disclosed can be embodied, at least in part, in software. That is, the techniques may be carried out in a computer system or other data processing system in response to its processor, such as a microprocessor, executing sequences of instructions contained in a memory, such as ROM, volatile RAM, non-volatile memory, cache or a remote storage device.

Routines executed to implement the embodiments may be implemented as part of an operating system or a specific application, component, program, object, module or sequence of instructions referred to as “computer programs.” The computer programs typically include one or more instructions set at various times in various memory and storage devices in a computer, and that, when read and executed by one or more processors in a computer, cause the computer to perform operations necessary to execute elements involving the various aspects.

A machine readable medium can be used to store software and data which when executed by a data processing system causes the system to perform various methods. The executable software and data may be stored in various places including for example ROM, volatile RAM, non-volatile memory and/or cache. Portions of this software and/or data may be stored in any one of these storage devices. Further, the data and instructions can be obtained from centralized servers or peer to peer networks. Different portions of the data and instructions can be obtained from different centralized servers and/or peer to peer networks at different times and in different communication sessions or in a same communication session. The data and instructions can be obtained in entirety prior to the execution of the applications. Alternatively, portions of the data and instructions can be obtained dynamically, just in time, when needed for execution. Thus, it is not required that the data and instructions be on a machine readable medium in entirety at a particular instance of time.

Examples of computer-readable media include but are not limited to recordable and non-recordable type media such as volatile and non-volatile memory devices, read only memory (ROM), random access memory (RAM), flash memory devices, floppy and other removable disks, magnetic disk storage media, optical storage media (e.g., Compact Disk Read-Only Memory (CD ROMS), Digital Versatile Disks (DVDs), etc.), among others. The computer-readable media may store the instructions.

The instructions may also be embodied in digital and analog communication links for electrical, optical, acoustical or other forms of propagated signals, such as carrier waves, infrared signals, digital signals, etc. However, propagated signals, such as carrier waves, infrared signals, digital signals, etc. are not tangible machine readable medium and are not configured to store instructions.

In general, a tangible machine readable medium includes any apparatus that provides (e.g., stores and/or transmits) information in a form accessible by a machine (e.g., a computer, network device, personal digital assistant, manufacturing tool, any device with a set of one or more processors, etc.).

In various embodiments, hardwired circuitry may be used in combination with software instructions to implement the techniques. Thus, the techniques are neither limited to any specific combination of hardware circuitry and software nor to any particular source for the instructions executed by the data processing system.

Although some of the drawings illustrate a number of operations in a particular order, operations which are not order dependent may be reordered and other operations may be combined or broken out. While some reordering or other groupings are specifically mentioned, others will be apparent to those of ordinary skill in the art and so do not present an exhaustive list of alternatives. Moreover, it should be recognized that the stages could be implemented in hardware, firmware, software or any combination thereof.

In the foregoing specification, the disclosure has been described with reference to specific embodiments thereof. It will be evident that various modifications may be made thereto without departing from the broader spirit and scope as set forth in the following claims. The specification and drawings are, accordingly, to be regarded in an illustrative sense rather than a restrictive sense. 

1. A computer-implemented method, comprising: receiving, in a computing device, a request to make a payment to a merchant using funds associated with a phone number; determining, using the computing device, whether to skip mobile communications with a mobile phone at the phone number to confirm the request; in response to a determination to not skip the mobile communications, communicating with the mobile phone at the phone number to confirm the request; and in response to a determination to skip the mobile communications, billing a user of the phone number using a funding source associated with the phone number without the communicating with the mobile phone.
 2. The method of claim 1, wherein the determining is based on historical transaction data associated with the phone number and information associated with the request.
 3. The method of claim 1, further comprising: providing a user interface to allow the user to select a preference option to skip the mobile communications; and storing the preference option selected by the user in association with the phone number after the user selects the preference option.
 4. The method of claim 3, further comprising: communicating with the mobile phone to confirm the selection of the preference option in response to the user selecting the preference option.
 5. The method of claim 4, wherein the determining of whether to skip the mobile communications is based at least in part on the preference option.
 6. The method of claim 4, wherein the determining of whether to skip the mobile communications is further based on regulatory rules.
 7. The method of claim 4, further comprising: determining a risk of skipping the mobile communications, wherein the determining of whether to skip the mobile communications is further based on the risk.
 8. The method of claim 1, wherein the determining of whether to skip the mobile communications is based on at least one identifier of the user and at least one identifier of a device of the user.
 9. The method of claim 1, wherein the determining of whether to skip the mobile communications is based on a type of the funding source for the payment.
 10. The method of claim 1, wherein the determining of whether to skip the mobile communications is based on information about the user received from the merchant in connection with the request.
 11. The method of claim 1, wherein the determining of whether to skip the mobile communications is based on information related to a social graph of the user.
 12. The method of claim 1, wherein the communicating comprises: transmitting a message to the mobile phone at the phone number.
 13. The method of claim 1, wherein the communicating comprises: receiving a message from the mobile phone at the phone number.
 14. The method of claim 1, wherein the billing comprises: transmitting one or more premium messages to the mobile phone at the phone number to collect funds via a telecommunication carrier of the phone number.
 15. The method of claim 1, wherein the billing comprises: charging a bank account associated with the phone number.
 16. The method of claim 15, wherein the bank account is one of: a credit account, a debit account, a prepaid account, a checking account, and a savings account.
 17. A machine readable medium storing instructions, the instruction causing a computer to perform a method, the method comprising: receiving, in a computer, a request to make a payment to a merchant using funds associated with a phone number; determining, using the computer, whether to skip mobile communications with a mobile phone at the phone number to confirm the request; in response to a determination to not skip the mobile communications, communicating with the mobile phone at the phone number to confirm the request; and in response to a determination to skip the mobile communications, billing a user of the phone number using a funding source associated with the phone number without the communicating with the mobile phone.
 18. A system, comprising: a data storage facility to store information associated with a phone number; and an interchange coupled with the data storage facility, the interchange including a common format processor and a plurality of converters to interface with a plurality of controllers, the converters configured to communicate with the controllers in different formats, the converts to communicate with the common format processor in a common format; wherein after a payment request identifying the phone number is received in the interchange, the common format processor is to determine whether to skip mobile communications with a mobile phone at the phone number to confirm the request; wherein, in response to a determination to not skip the mobile communications, the common format processor is to use one of the converters to communicate with the mobile phone at the phone number to confirm the request; and wherein, in response to a determination to skip the mobile communications, the interchange is to bill a user of the phone number using a funding source associated with the phone number without communicating with the mobile phone for authorization of a payment to a merchant in accordance with the payment request.
 19. The system of claim 18, wherein the interchange is to receive information about the user from a server of the merchant in connection with the payment request.
 20. The system of claim 18, wherein the common format processor is configured to generate a risk profile for the user based on the information associated with the phone number in the data storage facility and to determine whether to skip the mobile communications based at least in part on the risk profile. 